Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1124

reference: 677-tree-1
name: 1124
tree-preservation-order: undefined
677-tpo-1
uprn
address-text
point: POINT (-1.017940 50.879873)
geometry: MULTIPOLYGON (((-1.017898 50.879869,-1.017899 50.879877,-1.017905 50.879885,-1.017915 50.879891,-1.017926 50.879895,-1.017940 50.879896,-1.017953 50.879895,-1.017965 50.879891,-1.017974 50.879885,-1.017981 50.879878,-1.017983 50.879869,-1.017981 50.879861,-1.017975 50.879853,-1.017966 50.879847,-1.017954 50.879843,-1.017941 50.879842,-1.017928 50.879843,-1.017916 50.879847,-1.017906 50.879853,-1.017900 50.879860,-1.017898 50.879869)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL